This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@objectstack/cli@7.8.0

Minor Changes

• 6b60068: fix(cli): objectstack dev persists data by default (no more :memory: wipe on restart)

  objectstack dev historically fell back to a :memory: SQLite database when no --database / OS_DATABASE_URL was given, so every restart silently wiped all data and AI-authored metadata — you'd build an app, restart, and it would be gone, which makes local app-building unusable.

  dev now defaults to a persistent, project-anchored SQLite file at <cwd>/.objectstack/data/dev.db (gitignored, per-project). Existing opt-outs are unchanged and take precedence: --fresh (ephemeral temp DB), --database <url>, OS_DATABASE_URL/DATABASE_URL, or an explicit in-memory driver (--database-driver memory / OS_DATABASE_DRIVER=memory). Resolution is extracted into the testable resolveDefaultDevDbUrl() helper.

  The app-showcase example drops its explicit :memory: datasource override (which would otherwise route data back to memory and defeat the new default), so it persists across restarts out of the box.

Patch Changes

• Updated dependencies [6b82e68]
• Updated dependencies [06f2bbb]
• Updated dependencies [a75823a]
• Updated dependencies [4fbb86a]
• Updated dependencies [e631f1e]
• Updated dependencies [328a7c4]
• Updated dependencies [f01f9fa]
• Updated dependencies [4888ea2]
• Updated dependencies [6fc2678]
• Updated dependencies [36719db]
• Updated dependencies [424ab26]
  • @objectstack/service-ai@7.8.0
  • @objectstack/spec@7.8.0
  • @objectstack/objectql@7.8.0
  • @objectstack/rest@7.8.0
  • @objectstack/runtime@7.8.0
  • @objectstack/service-package@7.8.0
  • @objectstack/formula@7.8.0
  • @objectstack/account@7.8.0
  • @objectstack/client@7.8.0
  • @objectstack/core@7.8.0
  • @objectstack/observability@7.8.0
  • @objectstack/platform-objects@7.8.0
  • @objectstack/driver-memory@7.8.0
  • @objectstack/driver-mongodb@7.8.0
  • @objectstack/driver-sql@7.8.0
  • @objectstack/driver-sqlite-wasm@7.8.0
  • @objectstack/plugin-approvals@7.8.0
  • @objectstack/plugin-audit@7.8.0
  • @objectstack/plugin-auth@7.8.0
  • @objectstack/plugin-email@7.8.0
  • @objectstack/plugin-hono-server@7.8.0
  • @objectstack/plugin-mcp-server@7.8.0
  • @objectstack/plugin-org-scoping@7.8.0
  • @objectstack/plugin-reports@7.8.0
  • @objectstack/plugin-security@7.8.0
  • @objectstack/plugin-sharing@7.8.0
  • @objectstack/plugin-trigger-record-change@7.8.0
  • @objectstack/plugin-trigger-schedule@7.8.0
  • @objectstack/plugin-webhooks@7.8.0
  • @objectstack/service-analytics@7.8.0
  • @objectstack/service-automation@7.8.0
  • @objectstack/service-cache@7.8.0
  • @objectstack/service-datasource@7.8.0
  • @objectstack/service-feed@7.8.0
  • @objectstack/service-job@7.8.0
  • @objectstack/service-messaging@7.8.0
  • @objectstack/service-queue@7.8.0
  • @objectstack/service-realtime@7.8.0
  • @objectstack/service-settings@7.8.0
  • @objectstack/service-storage@7.8.0
  • @objectstack/types@7.8.0
  • @objectstack/console@7.8.0

@objectstack/objectql@7.8.0

Minor Changes

• a75823a: feat(metadata): expose pending DRAFT metadata (ADR-0033 draft discoverability)

  AI-authored metadata lands as drafts (sys_metadata rows with state='draft', bound to an app package), but the only list path — getMetaItems — reads the active registry, so drafts were invisible: a just-built app package looked empty and there was no "pending changes" surface.

  • SysMetadataRepository.listDrafts({type?, packageId?}) lists draft rows (mirrors list() but scoped to state='draft', optionally narrowed by package), returning a light header projection (no body) with packageId.
  • protocol.listDrafts({packageId?, type?, organizationId?}) exposes it over the overlay repo.
  • GET /api/v1/meta/_drafts?packageId=&type= surfaces it to the console. Registered in the REST server before the greedy /meta/:type route (and mirrored in the dispatcher) so _drafts is never captured as a metadata type name.

  Read-only; no behavior change to existing list/publish paths. Powers the upcoming Studio "drafts/pending changes" view and draft-aware package contents.

• 4fbb86a: feat(packages): consolidate the package subsystem so AI-built app packages surface in Studio

  The package subsystem was split across two stores that never met: the in-memory
  SchemaRegistry (what the dispatcher's /api/v1/packages list/detail and
  getMetaItems({type:'package'}) read — i.e. Studio's package selector) and the durable
  sys_packages table (where the AI's auto app package, and any package-service publish,
  were written). Nothing reconciled the two, so an AI-created app.<name> package never
  appeared in Studio.

  This unifies them around one write primitive and one read source:

  • protocol.installPackage is now implemented (it was declared-but-missing). It is the
    single canonical write path: it registers the package in the in-memory registry and
    best-effort persists it to sys_packages via the package service. Non-fatal when no
    package service is wired (registry write still succeeds).
  • Dispatcher POST /api/v1/packages routes through protocol.installPackage (falling
    back to the bare registry write when the protocol is unavailable), so HTTP installs are
    durable too.
  • @objectstack/service-package reconciles sys_packages back into the registry on
    boot, without clobbering filesystem-registered packages — so persisted packages survive a
    restart and stay visible in the registry-backed read paths.
  • @objectstack/service-ai apply_blueprint now homes an app via
    protocol.installPackage (falling back to the legacy package-service publish), so the
    app package lands where Studio reads it.

  Still the legacy package_id plane — sealed sys_package_version versioning and
  cross-environment promotion remain ADR-0027 follow-ups.

• e631f1e: feat(metadata): publish a whole app's drafts in one shot (ADR-0033)

  After an AI builds an app, its metadata is drafted (bound to an app package) and
  had to be published one item at a time. The package-level POST /packages/:id/publish
  needs the metadata service (503 when absent, e.g. the showcase) and reads the
  in-memory registry, not the drafts.

  • protocol.publishPackageDrafts({ packageId }) promotes every sys_metadata
    draft row bound to the package to active by reusing the per-item
    publishMetaItem primitive (overridable/lock guards + runtime registry
    refresh). Per-item failures are collected, not fatal. No metadata-service
    dependency.
  • POST /api/v1/packages/:id/publish-drafts exposes it (distinct from the
    registry-based /publish), returning { success, publishedCount, failedCount, published, failed }.

  Verified live: an AI-built app.asset_management (4 drafts) published in one call —
  all 4 promoted to active, drafts cleared, draft objects became queryable.

• 36719db: fix: AI-built apps are usable immediately — sync new object tables on publish + emit valid kanban config

  Two gaps found by end-to-end testing of an AI-built app:

  1. A freshly-published object couldn't accept records until a server restart. Publishing a drafted object registered it in the in-memory registry but never created its physical table (table sync only ran at boot), so inserts failed with object_not_found ("no such table"). Added ObjectQL.syncObjectSchema(name) (a targeted, idempotent single-object schema sync) and call it from the publish paths (protocol.publishMetaItem and saveMetaItem mode:'publish', via ensureObjectStorage). Best-effort + non-fatal. New objects are now CRUD-able the moment they're published.

  2. AI-generated kanban views rendered as plain lists (and sometimes failed validation). The blueprint viewBody emitted list.type:'kanban' with no kanban config; KanbanConfigSchema requires groupByField and columns. Added an optional groupBy to the blueprint view schema (lenient + strict) and have apply_blueprint set list.kanban = { groupByField, columns } — using the view's explicit groupBy when given, else inferring the object's first select field. AI-built kanban views now validate, publish, and carry a real group-by field.

Patch Changes

• 6fc2678: fix(metadata): stamp a top-level name on view bodies at the write path so AI/hand-authored views surface

  getMetaItems only overlays a sys_metadata row when its parsed body has a top-level name. Some view producers — notably loose { list: <ListView> } / { form: … } fragments that AI tools and hand-authoring emit — pass schema validation but carry no top-level name, so the view was silently dropped from the object's view list and never appeared as a tab ("validates ≠ surfaces").

  saveMetaItem now guarantees a top-level name on every view body at the single write chokepoint, BEFORE validation + persistence, so a nameless view is auto-corrected regardless of which authoring path produced it. It deliberately does NOT reshape the document: both the defineView container form ({ list, listViews, … }, expanded by the loader) and the { name, object, viewKind, config } record form are valid and the console consumes both — reshaping a container into a record risks producing an invalid record (e.g. a non-<object>.<key> name) and drops Studio-only fields (isPinned, sortOrder, …). Exported as normalizeViewMetadata and unit-tested.

  (Note for follow-up: the view metadata schema is itself a permissive union — it accepts an unknown viewKind, a kanban config missing groupByField, even {}. Tightening it correctly requires first consolidating the four legitimate view shapes — record / container / flat list / flat form — and is a separate spec change.)

• Updated dependencies [06f2bbb]

• Updated dependencies [f01f9fa]

• Updated dependencies [36719db]

• Updated dependencies [424ab26]

  • @objectstack/spec@7.8.0
  • @objectstack/formula@7.8.0
  • @objectstack/core@7.8.0
  • @objectstack/metadata-core@7.8.0
  • @objectstack/types@7.8.0

@objectstack/service-ai@7.8.0

Minor Changes

• 6b82e68: feat(ai): zero-package app building — auto-home a blueprint's app in a writable package

  When the AI blueprint flow builds an app, it now silently gives that app a writable "home" package (one app ⇒ one app.<name> package) and binds every drafted artifact (objects, views, dashboards, the app) to it — so a business user never has to create a "package" to start building (the mainstream AI-builder UX: Power Apps' default solution, Salesforce orgs). Packaging/versioning stays an opt-in, later concern.

  • apply_blueprint ensures the app package up front (idempotent: reuse if it exists, else create via the runtime package service) and threads its packageId through every stageDraft → sys_metadata.package_id. The result envelope gains package: { id, name, created }.
  • The package service is resolved lazily (per call, not at plugin-init time) so it works regardless of service-init order and picks up the opt-in marketplace capability when present.
  • Best-effort, non-fatal: if no package service is wired, drafting proceeds package-less exactly as before — the build never fails on packaging.

  Scope/caveats: this stamps the legacy sys_metadata.package_id (a real grouping + the foundation for later version/export/promote), not the sealed sys_package_version model — full cross-environment promotion and Studio package-selector visibility depend on finishing the runtime package subsystem (ADR-0027), tracked separately. (The showcase example enables the marketplace capability to exercise this.)

• 4888ea2: feat(ai): add get_metadata_schema tool so the agent can read a type's contract before authoring

  The metadata-authoring agent never sees the real spec Zod schemas — it works against a simplified blueprint or sends a free-form definition and only learns the true shape from post-hoc validation errors. For complex types (view, dashboard, flow, …) that means guessing, e.g. a kanban view's required kanban: { groupByField, columns } block.

  New get_metadata_schema tool returns the JSON Schema (via Zod v4's toJSONSchema) derived from the SAME live schema saveMetaItem validates against (getMetadataTypeSchema). The metadata_authoring skill now instructs the agent to call it before authoring a non-trivial type, so it conforms first time instead of trial-and-error. Read-only; resolves plural type names; returns a graceful error for types that can't be serialized (e.g. object, which the dedicated create_object tools cover anyway).

• 36719db: fix: AI-built apps are usable immediately — sync new object tables on publish + emit valid kanban config

  Two gaps found by end-to-end testing of an AI-built app:

  1. A freshly-published object couldn't accept records until a server restart. Publishing a drafted object registered it in the in-memory registry but never created its physical table (table sync only ran at boot), so inserts failed with object_not_found ("no such table"). Added ObjectQL.syncObjectSchema(name) (a targeted, idempotent single-object schema sync) and call it from the publish paths (protocol.publishMetaItem and saveMetaItem mode:'publish', via ensureObjectStorage). Best-effort + non-fatal. New objects are now CRUD-able the moment they're published.

  2. AI-generated kanban views rendered as plain lists (and sometimes failed validation). The blueprint viewBody emitted list.type:'kanban' with no kanban config; KanbanConfigSchema requires groupByField and columns. Added an optional groupBy to the blueprint view schema (lenient + strict) and have apply_blueprint set list.kanban = { groupByField, columns } — using the view's explicit groupBy when given, else inferring the object's first select field. AI-built kanban views now validate, publish, and carry a real group-by field.

Patch Changes

• 06f2bbb: fix(ai): make ADR-0033 blueprint authoring work with OpenAI structured outputs

  Two bugs surfaced by a live end-to-end run (Studio chat → blueprint → draft → review → publish) against a real model (OpenAI via the Vercel AI Gateway) — both invisible to the existing unit tests:

  1. propose_blueprint failed against OpenAI strict structured outputs. SolutionBlueprintSchema uses optional fields and a free-form seedData record; OpenAI's strict mode requires every property listed in required and rejects open additionalProperties, so generateObject errored ('required' … must include every key in properties) and the agent silently fell back to free-text. Adds SolutionBlueprintStrictSchema — a strict-compatible mirror (optional → nullable, no z.record) used only as the generateObject output contract. The lenient SolutionBlueprintSchema (and every existing consumer/test) is unchanged; the blueprint tools strip the nulls the strict contract emits so downstream stays clean.

  2. Tool-only assistant turns failed to persist. ai_messages.content is required, but an assistant turn that only calls a tool has no text, so the insert failed, the turn was dropped, and the next turn lost context (the agent re-proposed instead of applying the confirmed blueprint). ObjectQLConversationService.addMessage now synthesizes a readable placeholder from the tool names ((called propose_blueprint)) plus a defensive non-empty fallback.

  With both fixes the full plan-first loop runs end-to-end on OpenAI models: propose → confirm → batch-draft objects/views/dashboards/app → review/diff → publish.

• 4fbb86a: feat(packages): consolidate the package subsystem so AI-built app packages surface in Studio

  The package subsystem was split across two stores that never met: the in-memory
  SchemaRegistry (what the dispatcher's /api/v1/packages list/detail and
  getMetaItems({type:'package'}) read — i.e. Studio's package selector) and the durable
  sys_packages table (where the AI's auto app package, and any package-service publish,
  were written). Nothing reconciled the two, so an AI-created app.<name> package never
  appeared in Studio.

  This unifies them around one write primitive and one read source:

  • protocol.installPackage is now implemented (it was declared-but-missing). It is the
    single canonical write path: it registers the package in the in-memory registry and
    best-effort persists it to sys_packages via the package service. Non-fatal when no
    package service is wired (registry write still succeeds).
  • Dispatcher POST /api/v1/packages routes through protocol.installPackage (falling
    back to the bare registry write when the protocol is unavailable), so HTTP installs are
    durable too.
  • @objectstack/service-package reconciles sys_packages back into the registry on
    boot, without clobbering filesystem-registered packages — so persisted packages survive a
    restart and stay visible in the registry-backed read paths.
  • @objectstack/service-ai apply_blueprint now homes an app via
    protocol.installPackage (falling back to the legacy package-service publish), so the
    app package lands where Studio reads it.

  Still the legacy package_id plane — sealed sys_package_version versioning and
  cross-environment promotion remain ADR-0027 follow-ups.

• 328a7c4: fix(ai): AI-authored views now bind to their object and render (kanban as a board, not a list)

  An AI-built app's views (including kanban) appeared only as the default list and never as selectable tabs. Diagnosis (vs the working showcase kanban) showed it was a metadata-shape bug in the blueprint's viewBody, not the renderer or skill: it emitted a bare { list: {…} } fragment instead of the canonical view record. Three things were missing/wrong:

  • no top-level name → getMetaItems only surfaces overlay rows whose body has name, so every AI view was silently dropped from the object's view list;
  • no top-level object / viewKind → the console couldn't bind the view to its object;
  • the view name wasn't <object>.<key>-prefixed (the convention the console keys view tabs off).

  viewBody now emits { name: '<object>.<key>', object, viewKind: 'list'|'form', config: <ListView|FormView> }, matching the shape the showcase's own views use (verified against the real ViewSchema). End-to-end verified: an AI-built kanban app surfaces 看板 + 列表 as tabs and renders the kanban as a board grouped by status.

• Updated dependencies [06f2bbb]

• Updated dependencies [f01f9fa]

• Updated dependencies [36719db]

• Updated dependencies [424ab26]

  • @objectstack/spec@7.8.0
  • @objectstack/formula@7.8.0
  • @objectstack/core@7.8.0
  • @objectstack/types@7.8.0

@objectstack/spec@7.8.0

Minor Changes

• 36719db: fix: AI-built apps are usable immediately — sync new object tables on publish + emit valid kanban config

  Two gaps found by end-to-end testing of an AI-built app:

  1. A freshly-published object couldn't accept records until a server restart. Publishing a drafted object registered it in the in-memory registry but never created its physical table (table sync only ran at boot), so inserts failed with object_not_found ("no such table"). Added ObjectQL.syncObjectSchema(name) (a targeted, idempotent single-object schema sync) and call it from the publish paths (protocol.publishMetaItem and saveMetaItem mode:'publish', via ensureObjectStorage). Best-effort + non-fatal. New objects are now CRUD-able the moment they're published.

  2. AI-generated kanban views rendered as plain lists (and sometimes failed validation). The blueprint viewBody emitted list.type:'kanban' with no kanban config; KanbanConfigSchema requires groupByField and columns. Added an optional groupBy to the blueprint view schema (lenient + strict) and have apply_blueprint set list.kanban = { groupByField, columns } — using the view's explicit groupBy when given, else inferring the object's first select field. AI-built kanban views now validate, publish, and carry a real group-by field.

Patch Changes

• 06f2bbb: fix(ai): make ADR-0033 blueprint authoring work with OpenAI structured outputs

  Two bugs surfaced by a live end-to-end run (Studio chat → blueprint → draft → review → publish) against a real model (OpenAI via the Vercel AI Gateway) — both invisible to the existing unit tests:

  1. propose_blueprint failed against OpenAI strict structured outputs. SolutionBlueprintSchema uses optional fields and a free-form seedData record; OpenAI's strict mode requires every property listed in required and rejects open additionalProperties, so generateObject errored ('required' … must include every key in properties) and the agent silently fell back to free-text. Adds SolutionBlueprintStrictSchema — a strict-compatible mirror (optional → nullable, no z.record) used only as the generateObject output contract. The lenient SolutionBlueprintSchema (and every existing consumer/test) is unchanged; the blueprint tools strip the nulls the strict contract emits so downstream stays clean.

  2. Tool-only assistant turns failed to persist. ai_messages.content is required, but an assistant turn that only calls a tool has no text, so the insert failed, the turn was dropped, and the next turn lost context (the agent re-proposed instead of applying the confirmed blueprint). ObjectQLConversationService.addMessage now synthesizes a readable placeholder from the tool names ((called propose_blueprint)) plus a defensive non-empty fallback.

  With both fixes the full plan-first loop runs end-to-end on OpenAI models: propose → confirm → batch-draft objects/views/dashboards/app → review/diff → publish.

• 424ab26: fix(seed): reject object-wrapped relationship references and constrain them at compile time

  Seed datasets resolve lookup / master_detail references by matching the value
  against the target record's externalId — so the value must be the plain natural-key
  string (e.g. account: 'Acme Corp'), never a wrapper object like
  account: { externalId: 'Acme Corp' }. The wrapper was silently skipped by the
  loader, fell through unresolved, and reached the SQL driver as a non-bindable value —
  masked on an always-empty :memory: DB but crashing on a persistent one with
  "SQLite3 can only bind numbers, strings, bigints, buffers, and null" once seeds re-ran
  as updates.

  • defineDataset now constrains reference fields to string | null at compile time
    (derived from each field's type), so the object form is a type error.
  • SeedLoaderService now fails loudly with an actionable message (and drops the value
    instead of handing it to the driver) when a reference is an object — consistent
    behavior across all drivers, no longer silently masked.

@objectstack/express@7.8.0

Patch Changes

• Updated dependencies [a75823a]
• Updated dependencies [4fbb86a]
• Updated dependencies [e631f1e]
• Updated dependencies [424ab26]
  • @objectstack/runtime@7.8.0

@objectstack/fastify@7.8.0

Patch Changes

• Updated dependencies [a75823a]
• Updated dependencies [4fbb86a]
• Updated dependencies [e631f1e]
• Updated dependencies [424ab26]
  • @objectstack/runtime@7.8.0

@objectstack/hono@7.8.0

Patch Changes

• Updated dependencies [a75823a]
• Updated dependencies [4fbb86a]
• Updated dependencies [e631f1e]
• Updated dependencies [424ab26]
  • @objectstack/runtime@7.8.0
  • @objectstack/plugin-hono-server@7.8.0
  • @objectstack/types@7.8.0

@objectstack/nestjs@7.8.0

Patch Changes

• Updated dependencies [a75823a]
• Updated dependencies [4fbb86a]
• Updated dependencies [e631f1e]
• Updated dependencies [424ab26]
  • @objectstack/runtime@7.8.0

@objectstack/nextjs@7.8.0

Patch Changes

• Updated dependencies [a75823a]
• Updated dependencies [4fbb86a]
• Updated dependencies [e631f1e]
• Updated dependencies [424ab26]
  • @objectstack/runtime@7.8.0

@objectstack/nuxt@7.8.0

Patch Changes

• Updated dependencies [a75823a]
• Updated dependencies [4fbb86a]
• Updated dependencies [e631f1e]
• Updated dependencies [424ab26]
  • @objectstack/runtime@7.8.0

@objectstack/sveltekit@7.8.0

Patch Changes

• Updated dependencies [a75823a]
• Updated dependencies [4fbb86a]
• Updated dependencies [e631f1e]
• Updated dependencies [424ab26]
  • @objectstack/runtime@7.8.0

@objectstack/client@7.8.0

Patch Changes

• Updated dependencies [06f2bbb]
• Updated dependencies [36719db]
• Updated dependencies [424ab26]
  • @objectstack/spec@7.8.0
  • @objectstack/core@7.8.0

@objectstack/client-react@7.8.0

Patch Changes

• Updated dependencies [06f2bbb]
• Updated dependencies [36719db]
• Updated dependencies [424ab26]
  • @objectstack/spec@7.8.0
  • @objectstack/client@7.8.0
  • @objectstack/core@7.8.0

@objectstack/connector-mcp@7.8.0

Patch Changes

• Updated dependencies [06f2bbb]
• Updated dependencies [36719db]
• Updated dependencies [424ab26]
  • @objectstack/spec@7.8.0
  • @objectstack/core@7.8.0

@objectstack/connector-openapi@7.8.0

Patch Changes

• Updated dependencies [06f2bbb]
• Updated dependencies [36719db]
• Updated dependencies [424ab26]
  • @objectstack/spec@7.8.0
  • @objectstack/core@7.8.0

@objectstack/connector-rest@7.8.0

Patch Changes

• Updated dependencies [06f2bbb]
• Updated dependencies [36719db]
• Updated dependencies [424ab26]
  • @objectstack/spec@7.8.0
  • @objectstack/core@7.8.0

@objectstack/connector-slack@7.8.0

Patch Changes

• Updated dependencies [06f2bbb]
• Updated dependencies [36719db]
• Updated dependencies [424ab26]
  • @objectstack/spec@7.8.0
  • @objectstack/core@7.8.0

@objectstack/core@7.8.0

Patch Changes

• Updated dependencies [06f2bbb]
• Updated dependencies [36719db]
• Updated dependencies [424ab26]
  • @objectstack/spec@7.8.0

@objectstack/formula@7.8.0

Patch Changes

• f01f9fa: fix(formula): hydrate ISO date/datetime strings on CEL no such overload fault (Date-typed formula fields always evaluate to null — objectql applyFormulaPlan binds raw string values + silently swallows the CEL type fault (ADR-0032 §1c) #1530)

  Date-typed formula fields and date predicates always evaluated to null:
  Field.date/Field.datetime serialize to ISO strings, and cel-js compared the
  raw string against the google.protobuf.Timestamp from today()/now()/
  daysFromNow(), raising no such overload (swallowed to null). The existing
  numeric-string fault-retry (automation: flow conditions on numeric string-serialized fields (rating/currency/percent) fault under strict CEL and silently dead-end the flow (sibling of #1530) #1534) is now extended to also coerce strict ISO-8601
  date/date-time strings to Date before retrying once, fixing every caller
  (formula fields, flow conditions, validation/workflow predicates). Hydration runs
  only after a fault, so clean expressions are never re-interpreted and genuine
  non-temporal strings still fault loudly.

• Updated dependencies [06f2bbb]

• Updated dependencies [36719db]

• Updated dependencies [424ab26]

  • @objectstack/spec@7.8.0

@objectstack/metadata@7.8.0

Patch Changes

• Updated dependencies [06f2bbb]
• Updated dependencies [36719db]
• Updated dependencies [424ab26]
  • @objectstack/spec@7.8.0
  • @objectstack/core@7.8.0
  • @objectstack/metadata-core@7.8.0
  • @objectstack/platform-objects@7.8.0
  • @objectstack/types@7.8.0
  • @objectstack/metadata-fs@7.8.0

@objectstack/metadata-core@7.8.0

Patch Changes

• Updated dependencies [06f2bbb]
• Updated dependencies [36719db]
• Updated dependencies [424ab26]
  • @objectstack/spec@7.8.0

@objectstack/metadata-fs@7.8.0

Patch Changes

• @objectstack/metadata-core@7.8.0

@objectstack/observability@7.8.0

Patch Changes

• Updated dependencies [06f2bbb]
• Updated dependencies [36719db]
• Updated dependencies [424ab26]
  • @objectstack/spec@7.8.0

@objectstack/platform-objects@7.8.0

Patch Changes

• Updated dependencies [06f2bbb]
• Updated dependencies [36719db]
• Updated dependencies [424ab26]
  • @objectstack/spec@7.8.0
  • @objectstack/metadata-core@7.8.0

@objectstack/driver-memory@7.8.0

Patch Changes

• Updated dependencies [06f2bbb]
• Updated dependencies [36719db]
• Updated dependencies [424ab26]
  • @objectstack/spec@7.8.0
  • @objectstack/core@7.8.0

@objectstack/driver-mongodb@7.8.0

Patch Changes

• Updated dependencies [06f2bbb]
• Updated dependencies [36719db]
• Updated dependencies [424ab26]
  • @objectstack/spec@7.8.0
  • @objectstack/core@7.8.0

@objectstack/driver-sql@7.8.0

Patch Changes

• Updated dependencies [06f2bbb]
• Updated dependencies [36719db]
• Updated dependencies [424ab26]
  • @objectstack/spec@7.8.0
  • @objectstack/core@7.8.0

@objectstack/driver-sqlite-wasm@7.8.0

Patch Changes

• Updated dependencies [06f2bbb]
• Updated dependencies [36719db]
• Updated dependencies [424ab26]
  • @objectstack/spec@7.8.0
  • @objectstack/core@7.8.0
  • @objectstack/driver-sql@7.8.0

@objectstack/embedder-openai@7.8.0

Patch Changes

• Updated dependencies [06f2bbb]
• Updated dependencies [36719db]
• Updated dependencies [424ab26]
  • @objectstack/spec@7.8.0

@objectstack/knowledge-memory@7.8.0

Patch Changes

• Updated dependencies [06f2bbb]
• Updated dependencies [36719db]
• Updated dependencies [424ab26]
  • @objectstack/spec@7.8.0
  • @objectstack/core@7.8.0
  • @objectstack/service-knowledge@7.8.0

@objectstack/knowledge-ragflow@7.8.0

Patch Changes

• Updated dependencies [06f2bbb]
• Updated dependencies [36719db]
• Updated dependencies [424ab26]
  • @objectstack/spec@7.8.0
  • @objectstack/core@7.8.0
  • @objectstack/service-knowledge@7.8.0

@objectstack/plugin-approvals@7.8.0

Patch Changes

• Updated dependencies [06f2bbb]
• Updated dependencies [f01f9fa]
• Updated dependencies [36719db]
• Updated dependencies [424ab26]
  • @objectstack/spec@7.8.0
  • @objectstack/formula@7.8.0
  • @objectstack/core@7.8.0
  • @objectstack/metadata-core@7.8.0
  • @objectstack/platform-objects@7.8.0

@objectstack/plugin-audit@7.8.0

Patch Changes

• Updated dependencies [06f2bbb]
• Updated dependencies [36719db]
• Updated dependencies [424ab26]
  • @objectstack/spec@7.8.0
  • @objectstack/core@7.8.0
  • @objectstack/platform-objects@7.8.0

@objectstack/plugin-auth@7.8.0

Patch Changes

• Updated dependencies [06f2bbb]
• Updated dependencies [36719db]
• Updated dependencies [424ab26]
  • @objectstack/spec@7.8.0
  • @objectstack/core@7.8.0
  • @objectstack/platform-objects@7.8.0
  • @objectstack/types@7.8.0

@objectstack/plugin-dev@7.8.0

Patch Changes

• Updated dependencies [06f2bbb]
• Updated dependencies [a75823a]
• Updated dependencies [4fbb86a]
• Updated dependencies [e631f1e]
• Updated dependencies [6fc2678]
• Updated dependencies [36719db]
• Updated dependencies [424ab26]
  • @objectstack/spec@7.8.0
  • @objectstack/objectql@7.8.0
  • @objectstack/rest@7.8.0
  • @objectstack/runtime@7.8.0
  • @objectstack/core@7.8.0
  • @objectstack/driver-memory@7.8.0
  • @objectstack/plugin-auth@7.8.0
  • @objectstack/plugin-hono-server@7.8.0
  • @objectstack/plugin-org-scoping@7.8.0
  • @objectstack/plugin-security@7.8.0
  • @objectstack/service-i18n@7.8.0
  • @objectstack/types@7.8.0

@objectstack/plugin-email@7.8.0

Patch Changes

• Updated dependencies [06f2bbb]
• Updated dependencies [36719db]
• Updated dependencies [424ab26]
  • @objectstack/spec@7.8.0
  • @objectstack/core@7.8.0
  • @objectstack/platform-objects@7.8.0

@objectstack/plugin-hono-server@7.8.0

Patch Changes

• Updated dependencies [06f2bbb]
• Updated dependencies [36719db]
• Updated dependencies [424ab26]
  • @objectstack/spec@7.8.0
  • @objectstack/core@7.8.0
  • @objectstack/types@7.8.0

@objectstack/plugin-mcp-server@7.8.0

Patch Changes

• Updated dependencies [06f2bbb]
• Updated dependencies [36719db]
• Updated dependencies [424ab26]
  • @objectstack/spec@7.8.0
  • @objectstack/core@7.8.0
  • @objectstack/types@7.8.0

@objectstack/plugin-msw@7.8.0

Patch Changes

• Updated dependencies [06f2bbb]
• Updated dependencies [a75823a]
• Updated dependencies [4fbb86a]
• Updated dependencies [e631f1e]
• Updated dependencies [6fc2678]
• Updated dependencies [36719db]
• Updated dependencies [424ab26]
  • @objectstack/spec@7.8.0
  • @objectstack/objectql@7.8.0
  • @objectstack/runtime@7.8.0
  • @objectstack/core@7.8.0
  • @objectstack/types@7.8.0

@objectstack/plugin-org-scoping@7.8.0

Patch Changes

• Updated dependencies [06f2bbb]
• Updated dependencies [36719db]
• Updated dependencies [424ab26]
  • @objectstack/spec@7.8.0
  • @objectstack/core@7.8.0
  • @objectstack/platform-objects@7.8.0

@objectstack/plugin-reports@7.8.0

Patch Changes

• Updated dependencies [06f2bbb]
• Updated dependencies [36719db]
• Updated dependencies [424ab26]
  • @objectstack/spec@7.8.0
  • @objectstack/core@7.8.0
  • @objectstack/platform-objects@7.8.0

@objectstack/plugin-security@7.8.0

Patch Changes

• Updated dependencies [06f2bbb]
• Updated dependencies [36719db]
• Updated dependencies [424ab26]
  • @objectstack/spec@7.8.0
  • @objectstack/core@7.8.0
  • @objectstack/platform-objects@7.8.0

@objectstack/plugin-sharing@7.8.0

Patch Changes

• Updated dependencies [06f2bbb]
• Updated dependencies [a75823a]
• Updated dependencies [4fbb86a]
• Updated dependencies [e631f1e]
• Updated dependencies [6fc2678]
• Updated dependencies [36719db]
• Updated dependencies [424ab26]
  • @objectstack/spec@7.8.0
  • @objectstack/objectql@7.8.0
  • @objectstack/core@7.8.0
  • @objectstack/platform-objects@7.8.0

@objectstack/plugin-trigger-record-change@7.8.0

Patch Changes

• Updated dependencies [06f2bbb]
• Updated dependencies [36719db]
• Updated dependencies [424ab26]
  • @objectstack/spec@7.8.0
  • @objectstack/core@7.8.0

@objectstack/plugin-trigger-schedule@7.8.0

Patch Changes

• Updated dependencies [06f2bbb]
• Updated dependencies [36719db]
• Updated dependencies [424ab26]
  • @objectstack/spec@7.8.0
  • @objectstack/core@7.8.0

@objectstack/plugin-webhooks@7.8.0

Patch Changes

• Updated dependencies [06f2bbb]
• Updated dependencies [36719db]
• Updated dependencies [424ab26]
  • @objectstack/spec@7.8.0
  • @objectstack/core@7.8.0
  • @objectstack/service-messaging@7.8.0

@objectstack/rest@7.8.0

Patch Changes

• a75823a: feat(metadata): expose pending DRAFT metadata (ADR-0033 draft discoverability)

  AI-authored metadata lands as drafts (sys_metadata rows with state='draft', bound to an app package), but the only list path — getMetaItems — reads the active registry, so drafts were invisible: a just-built app package looked empty and there was no "pending changes" surface.

  • SysMetadataRepository.listDrafts({type?, packageId?}) lists draft rows (mirrors list() but scoped to state='draft', optionally narrowed by package), returning a light header projection (no body) with packageId.
  • protocol.listDrafts({packageId?, type?, organizationId?}) exposes it over the overlay repo.
  • GET /api/v1/meta/_drafts?packageId=&type= surfaces it to the console. Registered in the REST server before the greedy /meta/:type route (and mirrored in the dispatcher) so _drafts is never captured as a metadata type name.

  Read-only; no behavior change to existing list/publish paths. Powers the upcoming Studio "drafts/pending changes" view and draft-aware package contents.

• Updated dependencies [06f2bbb]

• Updated dependencies [4fbb86a]

• Updated dependencies [36719db]

• Updated dependencies [424ab26]

  • @objectstack/spec@7.8.0
  • @objectstack/service-package@7.8.0
  • @objectstack/core@7.8.0

@objectstack/runtime@7.8.0

Patch Changes

• a75823a: feat(metadata): expose pending DRAFT metadata (ADR-0033 draft discoverability)

  AI-authored metadata lands as drafts (sys_metadata rows with state='draft', bound to an app package), but the only list path — getMetaItems — reads the active registry, so drafts were invisible: a just-built app package looked empty and there was no "pending changes" surface.

  • SysMetadataRepository.listDrafts({type?, packageId?}) lists draft rows (mirrors list() but scoped to state='draft', optionally narrowed by package), returning a light header projection (no body) with packageId.
  • protocol.listDrafts({packageId?, type?, organizationId?}) exposes it over the overlay repo.
  • GET /api/v1/meta/_drafts?packageId=&type= surfaces it to the console. Registered in the REST server before the greedy /meta/:type route (and mirrored in the dispatcher) so _drafts is never captured as a metadata type name.

  Read-only; no behavior change to existing list/publish paths. Powers the upcoming Studio "drafts/pending changes" view and draft-aware package contents.

• 4fbb86a: feat(packages): consolidate the package subsystem so AI-built app packages surface in Studio

  The package subsystem was split across two stores that never met: the in-memory
  SchemaRegistry (what the dispatcher's /api/v1/packages list/detail and
  getMetaItems({type:'package'}) read — i.e. Studio's package selector) and the durable
  sys_packages table (where the AI's auto app package, and any package-service publish,
  were written). Nothing reconciled the two, so an AI-created app.<name> package never
  appeared in Studio.

  This unifies them around one write primitive and one read source:

  • protocol.installPackage is now implemented (it was declared-but-missing). It is the
    single canonical write path: it registers the package in the in-memory registry and
    best-effort persists it to sys_packages via the package service. Non-fatal when no
    package service is wired (registry write still succeeds).
  • Dispatcher POST /api/v1/packages routes through protocol.installPackage (falling
    back to the bare registry write when the protocol is unavailable), so HTTP installs are
    durable too.
  • @objectstack/service-package reconciles sys_packages back into the registry on
    boot, without clobbering filesystem-registered packages — so persisted packages survive a
    restart and stay visible in the registry-backed read paths.
  • @objectstack/service-ai apply_blueprint now homes an app via
    protocol.installPackage (falling back to the legacy package-service publish), so the
    app package lands where Studio reads it.

  Still the legacy package_id plane — sealed sys_package_version versioning and
  cross-environment promotion remain ADR-0027 follow-ups.

• e631f1e: feat(metadata): publish a whole app's drafts in one shot (ADR-0033)

  After an AI builds an app, its metadata is drafted (bound to an app package) and
  had to be published one item at a time. The package-level POST /packages/:id/publish
  needs the metadata service (503 when absent, e.g. the showcase) and reads the
  in-memory registry, not the drafts.

  • protocol.publishPackageDrafts({ packageId }) promotes every sys_metadata
    draft row bound to the package to active by reusing the per-item
    publishMetaItem primitive (overridable/lock guards + runtime registry
    refresh). Per-item failures are collected, not fatal. No metadata-service
    dependency.
  • POST /api/v1/packages/:id/publish-drafts exposes it (distinct from the
    registry-based /publish), returning { success, publishedCount, failedCount, published, failed }.

  Verified live: an AI-built app.asset_management (4 drafts) published in one call —
  all 4 promoted to active, drafts cleared, draft objects became queryable.

• 424ab26: fix(seed): reject object-wrapped relationship references and constrain them at compile time

  Seed datasets resolve lookup / master_detail references by matching the value
  against the target record's externalId — so the value must be the plain natural-key
  string (e.g. account: 'Acme Corp'), never a wrapper object like
  account: { externalId: 'Acme Corp' }. The wrapper was silently skipped by the
  loader, fell through unresolved, and reached the SQL driver as a non-bindable value —
  masked on an always-empty :memory: DB but crashing on a persistent one with
  "SQLite3 can only bind numbers, strings, bigints, buffers, and null" once seeds re-ran
  as updates.

  • defineDataset now constrains reference fields to string | null at compile time
    (derived from each field's type), so the object form is a type error.
  • SeedLoaderService now fails loudly with an actionable message (and drops the value
    instead of handing it to the driver) when a reference is an object — consistent
    behavior across all drivers, no longer silently masked.

• Updated dependencies [06f2bbb]

• Updated dependencies [a75823a]

• Updated dependencies [4fbb86a]

• Updated dependencies [e631f1e]

• Updated dependencies [f01f9fa]

• Updated dependencies [6fc2678]

• Updated dependencies [36719db]

• Updated dependencies [424ab26]

  • @objectstack/spec@7.8.0
  • @objectstack/objectql@7.8.0
  • @objectstack/rest@7.8.0
  • @objectstack/formula@7.8.0
  • @objectstack/core@7.8.0
  • @objectstack/metadata@7.8.0
  • @objectstack/observability@7.8.0
  • @objectstack/driver-memory@7.8.0
  • @objectstack/driver-sql@7.8.0
  • @objectstack/driver-sqlite-wasm@7.8.0
  • @objectstack/plugin-auth@7.8.0
  • @objectstack/plugin-org-scoping@7.8.0
  • @objectstack/plugin-security@7.8.0
  • @objectstack/service-cluster@7.8.0
  • @objectstack/service-i18n@7.8.0
  • @objectstack/types@7.8.0

@objectstack/service-analytics@7.8.0

Patch Changes

• Updated dependencies [06f2bbb]
• Updated dependencies [36719db]
• Updated dependencies [424ab26]
  • @objectstack/spec@7.8.0
  • @objectstack/core@7.8.0

@objectstack/service-automation@7.8.0

Patch Changes

• Updated dependencies [06f2bbb]
• Updated dependencies [f01f9fa]
• Updated dependencies [36719db]
• Updated dependencies [424ab26]
  • @objectstack/spec@7.8.0
  • @objectstack/formula@7.8.0
  • @objectstack/core@7.8.0

@objectstack/service-cache@7.8.0

Patch Changes

• Updated dependencies [06f2bbb]
• Updated dependencies [36719db]
• Updated dependencies [424ab26]
  • @objectstack/spec@7.8.0
  • @objectstack/core@7.8.0
  • @objectstack/observability@7.8.0

@objectstack/service-cluster@7.8.0

Patch Changes

• Updated dependencies [06f2bbb]
• Updated dependencies [36719db]
• Updated dependencies [424ab26]
  • @objectstack/spec@7.8.0
  • @objectstack/core@7.8.0

@objectstack/service-cluster-redis@7.8.0

Patch Changes

• Updated dependencies [06f2bbb]
• Updated dependencies [36719db]
• Updated dependencies [424ab26]
  • @objectstack/spec@7.8.0
  • @objectstack/service-cluster@7.8.0

@objectstack/service-datasource@7.8.0

Patch Changes

• Updated dependencies [06f2bbb]
• Updated dependencies [36719db]
• Updated dependencies [424ab26]
  • @objectstack/spec@7.8.0
  • @objectstack/core@7.8.0

@objectstack/service-feed@7.8.0

Patch Changes

• Updated dependencies [06f2bbb]
• Updated dependencies [36719db]
• Updated dependencies [424ab26]
  • @objectstack/spec@7.8.0
  • @objectstack/core@7.8.0

@objectstack/service-i18n@7.8.0

Patch Changes

• Updated dependencies [06f2bbb]
• Updated dependencies [36719db]
• Updated dependencies [424ab26]
  • @objectstack/spec@7.8.0
  • @objectstack/core@7.8.0

@objectstack/service-job@7.8.0

Patch Changes

• Updated dependencies [06f2bbb]
• Updated dependencies [36719db]
• Updated dependencies [424ab26]
  • @objectstack/spec@7.8.0
  • @objectstack/core@7.8.0
  • @objectstack/platform-objects@7.8.0

@objectstack/service-knowledge@7.8.0

Patch Changes

• Updated dependencies [06f2bbb]
• Updated dependencies [36719db]
• Updated dependencies [424ab26]
  • @objectstack/spec@7.8.0
  • @objectstack/core@7.8.0

@objectstack/service-messaging@7.8.0

Patch Changes

• Updated dependencies [06f2bbb]
• Updated dependencies [36719db]
• Updated dependencies [424ab26]
  • @objectstack/spec@7.8.0
  • @objectstack/core@7.8.0

@objectstack/service-package@7.8.0

Patch Changes

• 4fbb86a: feat(packages): consolidate the package subsystem so AI-built app packages surface in Studio

  The package subsystem was split across two stores that never met: the in-memory
  SchemaRegistry (what the dispatcher's /api/v1/packages list/detail and
  getMetaItems({type:'package'}) read — i.e. Studio's package selector) and the durable
  sys_packages table (where the AI's auto app package, and any package-service publish,
  were written). Nothing reconciled the two, so an AI-created app.<name> package never
  appeared in Studio.

  This unifies them around one write primitive and one read source:

  • protocol.installPackage is now implemented (it was declared-but-missing). It is the
    single canonical write path: it registers the package in the in-memory registry and
    best-effort persists it to sys_packages via the package service. Non-fatal when no
    package service is wired (registry write still succeeds).
  • Dispatcher POST /api/v1/packages routes through protocol.installPackage (falling
    back to the bare registry write when the protocol is unavailable), so HTTP installs are
    durable too.
  • @objectstack/service-package reconciles sys_packages back into the registry on
    boot, without clobbering filesystem-registered packages — so persisted packages survive a
    restart and stay visible in the registry-backed read paths.
  • @objectstack/service-ai apply_blueprint now homes an app via
    protocol.installPackage (falling back to the legacy package-service publish), so the
    app package lands where Studio reads it.

  Still the legacy package_id plane — sealed sys_package_version versioning and
  cross-environment promotion remain ADR-0027 follow-ups.

• Updated dependencies [06f2bbb]

• Updated dependencies [36719db]

• Updated dependencies [424ab26]

  • @objectstack/spec@7.8.0
  • @objectstack/core@7.8.0

@objectstack/service-queue@7.8.0

Patch Changes

• Updated dependencies [06f2bbb]
• Updated dependencies [36719db]
• Updated dependencies [424ab26]
  • @objectstack/spec@7.8.0
  • @objectstack/core@7.8.0
  • @objectstack/platform-objects@7.8.0

@objectstack/service-realtime@7.8.0

Patch Changes

• Updated dependencies [06f2bbb]
• Updated dependencies [36719db]
• Updated dependencies [424ab26]
  • @objectstack/spec@7.8.0
  • @objectstack/core@7.8.0
  • @objectstack/platform-objects@7.8.0

@objectstack/service-settings@7.8.0

Patch Changes

• Updated dependencies [06f2bbb]
• Updated dependencies [36719db]
• Updated dependencies [424ab26]
  • @objectstack/spec@7.8.0
  • @objectstack/core@7.8.0
  • @objectstack/platform-objects@7.8.0
  • @objectstack/types@7.8.0

@objectstack/service-storage@7.8.0

Patch Changes

• Updated dependencies [06f2bbb]
• Updated dependencies [36719db]
• Updated dependencies [424ab26]
  • @objectstack/spec@7.8.0
  • @objectstack/core@7.8.0
  • @objectstack/observability@7.8.0

@objectstack/types@7.8.0

Patch Changes

• Updated dependencies [06f2bbb]
• Updated dependencies [36719db]
• Updated dependencies [424ab26]
  • @objectstack/spec@7.8.0

@objectstack/account@7.8.0

@objectstack/console@7.8.0

create-objectstack@7.8.0

objectstack-vscode@7.8.0

@objectstack/example-crm@4.0.36

Patch Changes

• Updated dependencies [06f2bbb]
• Updated dependencies [a75823a]
• Updated dependencies [4fbb86a]
• Updated dependencies [e631f1e]
• Updated dependencies [36719db]
• Updated dependencies [424ab26]
  • @objectstack/spec@7.8.0
  • @objectstack/runtime@7.8.0

@objectstack/example-showcase@0.1.6

Patch Changes

• 6b60068: fix(cli): objectstack dev persists data by default (no more :memory: wipe on restart)

  objectstack dev historically fell back to a :memory: SQLite database when no --database / OS_DATABASE_URL was given, so every restart silently wiped all data and AI-authored metadata — you'd build an app, restart, and it would be gone, which makes local app-building unusable.

  dev now defaults to a persistent, project-anchored SQLite file at <cwd>/.objectstack/data/dev.db (gitignored, per-project). Existing opt-outs are unchanged and take precedence: --fresh (ephemeral temp DB), --database <url>, OS_DATABASE_URL/DATABASE_URL, or an explicit in-memory driver (--database-driver memory / OS_DATABASE_DRIVER=memory). Resolution is extracted into the testable resolveDefaultDevDbUrl() helper.

  The app-showcase example drops its explicit :memory: datasource override (which would otherwise route data back to memory and defeat the new default), so it persists across restarts out of the box.

• Updated dependencies [06f2bbb]

• Updated dependencies [a75823a]

• Updated dependencies [4fbb86a]

• Updated dependencies [e631f1e]

• Updated dependencies [36719db]

• Updated dependencies [424ab26]

  • @objectstack/spec@7.8.0
  • @objectstack/runtime@7.8.0
  • @objectstack/connector-rest@7.8.0
  • @objectstack/connector-slack@7.8.0

@example/app-todo@4.0.36

Patch Changes

• Updated dependencies [6b82e68]
• Updated dependencies [06f2bbb]
• Updated dependencies [a75823a]
• Updated dependencies [4fbb86a]
• Updated dependencies [e631f1e]
• Updated dependencies [328a7c4]
• Updated dependencies [4888ea2]
• Updated dependencies [6fc2678]
• Updated dependencies [36719db]
• Updated dependencies [424ab26]
  • @objectstack/service-ai@7.8.0
  • @objectstack/spec@7.8.0
  • @objectstack/objectql@7.8.0
  • @objectstack/runtime@7.8.0
  • @objectstack/client@7.8.0
  • @objectstack/metadata@7.8.0
  • @objectstack/driver-sqlite-wasm@7.8.0
  • @objectstack/knowledge-memory@7.8.0
  • @objectstack/service-knowledge@7.8.0